Skip to content

change: Drop Python 3.5 support #542

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Apr 20, 2021
Merged

change: Drop Python 3.5 support #542

merged 5 commits into from
Apr 20, 2021

Conversation

lahirumaramba
Copy link
Member

@lahirumaramba lahirumaramba commented Apr 13, 2021

RELEASE NOTE: Dropped support for Python 3.5. Developers should to use Python 3.6 or higher when deploying the Admin SDK.

@lahirumaramba lahirumaramba added the release:stage Stage a release candidate label Apr 13, 2021
@lahirumaramba lahirumaramba changed the title chore: Drop Python 3.5 support change: Drop Python 3.5 support Apr 13, 2021
Copy link
Contributor

@hiranya911 hiranya911 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I only had one suggestion.

Have you thought about how to release/version this? In the past we have bumped major version numbers when we discontinued support for a platform version. But GCP is following a more relaxed policy with respect to that (albeit unofficially).

# Fallback for Python 3.5
from _pytest.monkeypatch import MonkeyPatch
return MonkeyPatch()
return MonkeyPatch()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just return pytest.MonkeyPatch()?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like pytest.MonkeyPatch() works for pytest 6.2 and up. Our CIs use the latest version so I think it would be safe to update this code.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we just set pytest version to 6.2 and up in requirements.txt file?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea! Updated.

@lahirumaramba
Copy link
Member Author

Looks good. I only had one suggestion.

Have you thought about how to release/version this? In the past we have bumped major version numbers when we discontinued support for a platform version. But GCP is following a more relaxed policy with respect to that (albeit unofficially).

Thanks! I would prefer we do a major version bump to be consistent with our previous releases. Having said that, if we would rather align our releases with GCP policies a minor version bump would not be a big issue.

Copy link
Contributor

@hiranya911 hiranya911 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

My personal preference is to bump the major version as well. GCP policy on this issue is still a work in progress, and might take a while to materialize. In the meantime, I'd be ok with bumping the major version for this change.

@lahirumaramba
Copy link
Member Author

LGTM 👍

My personal preference is to bump the major version as well. GCP policy on this issue is still a work in progress, and might take a while to materialize. In the meantime, I'd be ok with bumping the major version for this change.

Sounds good! Let's do a major version bump for this then. Thanks!

@lahirumaramba lahirumaramba merged commit a6714a1 into master Apr 20, 2021
@lahirumaramba lahirumaramba deleted the lm-drop-py35 branch April 20, 2021 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:stage Stage a release candidate release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

EOL for Python 3.5
2 participants